Is there any value in segregating the four callbacks into a separate struct, have a full default replacement struct, and require in setter that they are all non-null? It might prevent an accidental "forgot to set one" situation by the BPA. But would not change the overall behavior.

I think I agree, it will make it cleaner. It is probably very unlikely a user will want to use custom callbacks for some, and defaults for others (and if a user really needs to, they can just set it manually to do so). I will make that update this evening.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.2% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud